This repository has been archived by the owner on Jan 1, 2020. It is now read-only.
Status code proposals #1
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I took a crack at a few encodings after discussion today. Very rough, but I wanted to get something down on "paper".
I also started thinking more broadly than our use case. We can still do dependency trees and whatnot, but for actual general codes, these may make sense. It includes allowed/disallowed codes, and what I think could be some other common use cases.
I'm going to push a few more things to this PR, but feel free to give your thoughts! Maybe this approach is too far off track, I dunno 馃槢
Also, probably best to view it rendered rather than in code 馃槈 https://github.com/Finhaven/EthereumStatusCodes/blob/tables/contracts/CodeTable.md